Add Access to Items

Configure data security for the different items users can access.

Note: If the More Security Around Data Access Management feature is enabled, you will need the Super Admin permission to perform this task. Not sure if you have this feature? Reach out to your administrator. For more information, see More security around data access management.

In a permission, you can configure data security for the different items users can access such as analytic objects, data sources, interviews, and benchmarks.

Access to Analytic objects

The first step in configuring data security is to choose the analytic objects that can be accessed in the solution. The analytic objects are organized into two categories: subjects and overlays.

  • Subjects include analytic objects like applicants, candidates, employees, and requisitions. When you add access to a subject, you'll also be granting access to any associated events and related objects. For example, when you add access to the Employee subject, you'll also be defining access to events such as Employee Exit and Pay Change Events as well as related objects such as Assignments and Certifications.

    Events and related objects are typically items that don't have any meaning without the subject. For example, it would not make sense to have access to the Employee Exit event (terminations) without having access to the employee data for the individual who was terminated. By default, events and related objects will inherit the data security configurations from the subject.

  • Overlays are a collection of aggregated data that are used to support key business comparisons. Overlays include analytic objects like Engagement and Benchmarks.

Access to sources

Note: Limited Availability This feature is in limited availability. If you are interested, please contact your Customer Success Manager.

You might configure data security to give access to data sources. Sources store data for your solution and are used to map to data load targets, such as analytic objects in Visier's data model. When you provide access to a source, you're granting access to data associated with the source. For example, if you grant access to the Employee source, any user assigned this permission can see all data ever uploaded to the Employee source.

Granting source access is particularly useful when you want to allow a user to onboard a new subject, such as uploading data, developing content in a project, and running data loads, while ensuring they only see the underlying data for the assigned subject and not others.

Users who are granted source access through permissions can:

  • Create and edit mappings.
  • View all data associated with a source.
  • View source configuration, but can't change the source configuration.
  • View data files that they uploaded to Visier, even if the files aren't connected to the sources that the user has access to.

Add items to a permission

  1. In a project, on the navigation bar, click Security > Permissions.

  2. Select a permission.
  3. In a permission, click the Data security tab and then click Add access.
  4. In the Select the data dialog, select the items that users with this permission can access and then click Finish.

    Result: Population and data access configurations appear for analytic objects. To configure custom population access, see Security Filters. To configure data access, see Data Access Sets.

  5. Optional: Restrict access to an event or related object for a subject by hovering over the analytic object and clicking the toggle button.

Remove access to items

  1. In a project, on the navigation bar, click Security > Permissions.

  2. Select a permission.
  3. In a permission, click the Data security tab.
  4. Hover over the item you want to remove access to and click the Remove access button .